Add feature to define frequencies to avoid - #20
Merged
Conversation
Added check for spectrum painting to skip spectrum paint if there is a conflict with any of the AvoidFreq ranges.
challengectl.py to check challenges against AvoidFreq ranges, and skip transmitting challenges if they conflict with the AvoidFreq ranges.
challenge types. Added challengetype to default case output to help with troubleshooting if that case is reached.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding a feature to define frequencies to avoid transmitting on. Frequencies to avoid can be defined as either channels with a center frequency and bandwidth, or by defining a lower and upper frequency limit.